\documentclass[12pt]{article}
\usepackage[top=2.5cm, bottom=2.5cm, left=2.5cm, right=2.5cm]{geometry}
\usepackage[pdfborder={0 0 0}]{hyperref}
\begin{document}
\begin{center}
\section*{Initial Plan}

Room Nanny

Embedded Systems Team

Evan Arnold, Edmund Chu, Chris Hale, Martin Young

20 Sept 2010
\end{center}

\subsection*{Team Profile}
Below are the individual qualifications and strengths of each member of the Embedded Systems Team.
\begin{itemize}
\item
\textbf{Evan Arnold}

Familiar with project management and labor division, as well as a variety of programming languages, including Java. Is able to, and effective at, filling gaps in team structure wherever needed.
\item
\textbf{Edmund Chu}

Qualified for documentation writing, algorithm design, Java programming and best practices.
\item
\textbf{Chris Hale}

Experienced with management for smaller projects, documentation writing, and creating visual representations and designs of software. He is also familiar with the Linux OS environment.

\item
\textbf{Martin Young}

Has a firm grasp of Java and will be most effective on the programming end of the project. In addition, he can abstract and generalize well and can make sound higher level design choices.
\end{itemize}

\subsection*{End Product}
Our end product, Room Nanny, is a system which collects and reports information about a room. A wireless device, a Sun SPOT, is placed in a room which then monitors the room temperature, if the lights are on or off, and opening and closing of a door. The Sun SPOT communicates this information to a base station, which then relays this information to a database system for storage.

This product will also include install documentation for the Sun SPOTs and base stations, development documentation about the construction of the system (especially useful in the case that future modifications need to be made), and overall product documentation for the client.

The following are the key features that our end product must include, along with feasible secondary features that may be implemented if resources are available.
\subsubsection*{Key Features}
\begin{enumerate}
\item
Collect data
\begin{itemize}
\item
Room temperature
\item
Ambient lights (on/off)
\item
Door movement
\end{itemize}
\item
Report data to database
\end{enumerate}
\subsubsection*{Secondary Features}
\begin{enumerate}
\item
Cosmetic: LEDs light up
\item
Push button to calibrate light sensitivity instead of hard coding values
\item
Utilizing both Sun SPOT devices to collect and send information from two locations
\item
Interpreting data (such as analysing door movement) before sending off to the database
\end{enumerate}

\subsection*{Tools}
\begin{enumerate}
\item
Development Tools
\begin{itemize}
\item
Google Code - For source code revision control and bug reporting. (Apache SVN will be used, with Mercurial as a fall-back.)

\url{http://www.googlecode.com/}
\item
NetBeans IDE - Development environment for working with Java.

\url{http://www.netbeans.com/}
\item
Java JDK, JRE, and Javadoc - Java Development Kit (JDK) and Java Runtime Environment (JRE) are necessary for programming with Java. Javadoc is a necessity for generating code documentation.

\url{http://www.java.com/}
\item
Sun SPOT Manager - Includes documentation, the Sun SPOT SDK, demo code, and NetBeans plugins for interfacing with the Sun SPOTS.

\url{http://www.sunspotworld.com/spotmanager/}
\end{itemize}
\item
Misc
\begin{itemize}
\item
Sun SPOT hardware, including the base station.
\item
Database to interface with ("our Client").
\item
Computer lab for monitoring and a server set up to interface with the base station.
\end{itemize}
\end{enumerate}

\subsection*{Challenges}
Our perceived challenges are primarily related to hardware interfacing:
\begin{itemize}
\item
Testing to make sure the Sun SPOT sensors are detecting levels correctly, and that we are interpreting them properly.
One thing we may do is bring in temperature sensing devices to act as a control.
\item
Learning how to use the Sun SPOT API/SDK. Careful studying of the documentation, the Sun SPOT World forums, and the provided demos should reveal how to do this.

\begin{itemize}
\item
Implementing wireless communication between the Sun SPOT and the base station.
\item
Retrieving data from the Sun SPOTs, and getting them to sync with the base station.
\item
Uploading software onto the Sun SPOTs.
\end{itemize}

\item
Communicating with the two other teams may also be challenging, although it may become less important once all the plans are finalized and everyone starts working on their own thing.
\end{itemize}

\subsection*{Milestones}
The following milestones are highly subject to be moved or expanded. These milestones are grouped by the integration dates (that have been previously been agreed upon) that they are expected to be met by.
\begin{enumerate}
\item
\textbf{September 28 - Integration 1}
\begin{enumerate}
\item
Communicate with database
\item
Retrieve data from emulated Sun SPOT
\item
Install documentation finished for the Sun SPOT Manager software
\end{enumerate}

\item
\textbf{October 21 - Integration 2}
\begin{enumerate}
\item
Develop API/software structure for code that talks between Sun SPOT devices and the database
\item
Load software onto physical Sun SPOT devices and retrieve real data.
(The Sun SPOT should work without communicating with a base station as an intermediary)
\item
Emulator documentation finished, Sun SPOT Manager software usage documentation finished
\end{enumerate}

\item
\textbf{November 9 - Integration 3}
\begin{enumerate}
\item
Ability to communicate between the base station and Sun SPOTS
\item
Send real data between all devices
\item
Accuracy verification of devices
\item
Accurately detect door opening and closing based on movement patterns
\item
Light sensitivity auto-calibration
\end{enumerate}

\item
\textbf{November 23 - Integration 4}
\begin{enumerate}
\item
Handling of both Sun SPOT devices for two different locations
\item
Finishing the remainder of any secondary features
\end{enumerate}

\item
\textbf{December 7 - Integration 5}
\begin{enumerate}
\item
Rough draft of end product documentation
\item
Stable build of end product
\end{enumerate}

\item
\textbf{December 13 - Integration 6} (Final Integration)
\begin{enumerate}
\item
End product documentation finished
\item
End product finished and ready for client
\end{enumerate}
\end{enumerate}

\end{document}